Secure and traceable security features for documents

ABSTRACT

A system for providing document authenticity, securing, and tracing includes a mark, an invisible code and a serial number. A user desiring to create a secure, verifiable document can receive one or more codes or indicia to put on the physical document.

INCORPORATION BY REFERENCE TO ANY PRIORITY APPLICATIONS

Any and all applications for which a foreign or domestic priority claimis identified in the Application Data Sheet as filed with the presentapplication are hereby incorporated by reference under 37 CFR 1.57. Thisapplication claims the benefit of priority of U.S. ProvisionalApplication No. 62/549,832, filed Aug. 24, 2017, the entire contents ofwhich are hereby incorporated by reference.

FIELD

This application relates to security features for documents.Specifically, this application relates to security features for physicaldocuments that are secure and traceable.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 depicts an embodiment of a document having a unique identifierthereon.

FIG. 2 depicts an embodiment of a display of a user interface.

FIG. 3 is a flow chart depicting an embodiment of a process for creatinga secure document.

FIG. 4 is a flow chart depicting an embodiment of a process for viewingsecure document information.

FIG. 5 is a flow chart depicting an exemplary process of ordering asecure document via a securing entity.

DETAILED DESCRIPTION

In the following detailed description, reference is made to theaccompanying drawings, which form a part thereof. In the drawings,similar symbols typically identify similar components, unless contextdictates otherwise. Thus, in some embodiments, part numbers may be usedfor similar components in multiple figures, or part numbers may varydepending from figure to figure. The illustrative embodiments describedin the detailed description, drawings, and claims are not meant to belimiting. Other embodiments may be utilized, and other changes may bemade, without departing from the spirit or scope of the subject matterpresented here. It will be readily understood that the aspects of thepresent disclosure, as generally described herein, and illustrated inthe Figures, can be arranged, substituted, combined, and designed in awide variety of different configurations, all of which are explicitlycontemplated and made part of this disclosure.

Physical documents can be counterfeited, illegally reproduced, altered,defaced, or stolen. Some documents, such as collectibles, memorabilia,vital records, census records, identification documents, governmentdocuments, photographs, and the like, have or derive value in beingauthentic and traceable. With the rise of imaging and reproductiontechnology, it is important to know whether a particular document is avalid, unaltered, legitimate document.

In one aspect, the present disclosure describes a system for ensuringdocuments are legitimate, to identify counterfeiting, and to providetraceability for documents. The data in each created document file isencrypted and digitally stored, and outputted as invisible physicalprinted matter.

One or more security features can be located on each secure document,which can include an emblem, a unique identifier, and an “invisible”code. The “invisible” code can be a code applied to a document using an“invisible” ink, such as an ink that fluoresces, phosphoresces,illuminates, or otherwise becomes visible upon interrogation with anappropriate signal or by using a specific method, filter, device, etc.The type of ink used to create the “invisible” code can be a singularink or combination of processes, including but not limited to, ink thatmay be developed by a chemical reaction process, or any of otherprocesses available. The invisible code can encode an ElectronicPostmark®, or EPM™, or an identifier for an EPM™, and can be similar tothose described with regard to U.S. application Ser. No. 15/066,945,filed Mar. 10, 2016, the entire contents of which is herein incorporatedby reference.

To provide security and to ensure authenticity of a document, such as acollectible, sports card, autograph, vital record, census record, votingballot, identification document (voter ID, driver license, socialsecurity card, or government issued ID, etc.), a government document, aphotograph, and the like, the document can have an emblem or mark, aunique identifier, and an invisible code applied to them. The emblem,unique identifier, and/or the invisible code are applied by theoriginator or creator of the document, or by an entity authorized by theoriginator or owner of the document. The unique identifier and theinvisible code are stored in a memory, such as a secure database. Theunique identifier acts as a unique serial number associated with andidentifying the specific document on which the unique identifier islocated. The invisible code identifies a digital tracking service, suchas an EPM™. A party can recognize that the document is protected ortracked for authenticity by seeing the emblem on the document. Theemblem can be an indicator that the document is protected or validatedusing systems described herein. In some embodiments, the emblem caninclude the unique identifier or an encoded identifier. In someembodiments, the emblem can be a computer readable emblem which itselfencodes a unique identifier, such as a digital badge or the like.

A user can access information about the document, such as originationdate, owner, etc., using the unique identifier. When the document isprocessed, such as by the United States Postal Service (USPS), oranother entity, the invisible code can be read using a specializedreader which can interrogate and read the invisible code, for example,using a barcode reader as installed in USPS post offices, or thoseauthorized by the US Postal Inspection Service. The USPS can also readthe unique identifier. The scan of the unique identifier and theinvisible code can be recorded in a record associated with the document.Actions, services, and the like that occur in the processing of thedocument can be stored in the record of the document which is associatedwith the invisible code and the unique identifier. In this way, adocument can be securely identified as authentic, securely tracked, andany alterations or counterfeiting identified. Document processing can beperformed on document processing equipment. Document processingequipment can include main processing equipment such as sorting or othersimilar equipment; imaging equipment and associated equipment; computersystems and scanners at retail locations such as stores, post offices,and the like; mobile computing devices; and any other suitable equipmentfor processing, reading, evaluating, or otherwise handling a document.

As used herein, the phrase “invisible code” can be understood to mean acode, such as a number, an alphanumeric string, or a computer readablecode which is not normally visible to the human eye. The invisible codecan be read when interrogated with a proper signal, such as when aparticular wavelength of light is shined on the invisible code or whenthe invisible code is interrogated with electromagnetic radiation havinga specific energy, spectrum, wavelength, and the like. Also as usedherein, the term “item” can refer to a physical document, a package orparcel, a mailpiece, or to any means of conveyance, such as a trays,containers, crates, boxes, bags, tags, vehicles, and the like. As usedherein, the phrase “secure document” can mean a document which hasparticular features, such as serial numbers, codes, and the like thatcan be used to verify or confirm authenticity. A secure document canhave an electronic record associated therewith which can provideinformation about the document's creation, ownership, and the like.

FIG. 1 depicts an embodiment of a document having authenticity andtraceability features thereon. A document 100 has a front 101 and a back102. Although the front 101 and back 102 would ordinarily be on oppositesides of the document 100, the front 101 and the back 102 in FIG. 1 areshown side-by-side for convenience. The front 101 includes an image 104.The image 104 can be an image, text, or any other information on thedocument 100, such as the contents of the vital record, census record,government ID, etc. For example, in the case of a collectible card, suchas a sports memorabilia card, the image 104 may be an image of anathlete or player, or of a team of athletes or players. In the exampleof a vital record, (i.e., government records that could include vitalinformation associated with personal identity such as Social Security,Date of Birth, Place of Birth, Signature, etc.). The image 104 caninclude the vital information, or in the case of a bank statement, theimage 104 can be the bank statement information. The image 104, asdescribed herein, need not be limited to a to an image, but couldinclude one or more images, text, numbers, or any combination of theabove. In some embodiments, the image 104 can be on both the front 101and the back 102. In some embodiments, such as in the case of a vitalrecord, the image 104 begins on the front 101 and continues on the back102.

The back 102 includes a mark 106, a serial number 107, an invisible code108 and a computer readable code 109. A person of skill in the art,guided by this disclosure, will understand that the document 100 caninclude one, all, or any combination of the mark 106, the serial number107, the invisible code 108, and the computer readable code 109.

The mark 106 is an icon, emblem, pattern, or image that identifies thedocument 100 as having security and traceability features thereon and/orassociated therewith. The mark 106 can signal to an entity, user, owner,or holder of the document 100, that the document 100 employs thesecurity and tracing system described herein. In some embodiments, themark 106 can include the serial number 107 and/or the computer readablecode 109.

The serial number 107 is a unique identifier assigned to, printed on,affixed to, or otherwise placed on the document 100. The serial number107 is an alphanumeric string, and is human readable. The computerreadable code 109 can be an encoded version of the serial number 107, orcan be another unique identifier associated with the serial number 107.In some embodiments, the computer readable code 109 can encodeinformation about the document 100, such as, for example, the date ofdocument creation, an identifier for a document originator, a deliverypoint for a recipient of the document 100, and the like. In someembodiments, the computer readable code can include a 5 to 11 digit ZIPcode or other similar code, if mailed outside the United States. In someembodiments, the computer readable code 109 can be an IMb™ code. In someembodiments, the document 100 does not include a computer readable code109. In some embodiments, the document 100 includes a computer readablecode 109 and no serial number 107.

The invisible code 108 can be an image, a computer readable code, suchas a barcode, QR code, and the like. The invisible code 108 can encode aunique identifier, which can be distinct from the serial number 107 andthe computer readable code 109. In some embodiments, the invisible code108 can encode an identifier for an EPM™. In some embodiments, theinvisible code 108 can encode or include a reference to or anassociation with the serial number 107 and/or the computer readable code109. The invisible code 108 is an encrypted code such that if theinvisible code 108 is read, it cannot be used to access any documentinformation (as will be described below) unless the reader has theproper decryption capabilities, or access to the decryption keys. Insome embodiments, the invisible code 108 can be printed over, within, orunderneath the mark 106.

The invisible code 108 can be applied to the document 100 using an inkor printing that is invisible to an un-aided human eye. The invisiblecode 108 can be read when interrogated with the proper wavelength oflight, to induce phosphorescence or luminescence. The inducedphosphorescence or luminescence can be a pattern, such as a computerreadable code, image, text string, and the like. The interrogationdevice, such as a scanner at a postal facility, can read the signal anddecode, or transmit the signal to another processor for decoding. Insome embodiments, the invisible code 108 is printed with a reflectiveink that reflects an interrogation signal with a specific wavelength orwith a specific pattern, which can be read and interpreted by aninterrogation device. The invisible code 108 can comprise an ink whichundergoes a stokes shift or an anti-stokes shift when interrogated byparticular wavelengths of light, shifting to a visible spectrum emissionwhen interrogated. The invisible code 108 is formulated with an ink thatcannot be easily reproduced, such as by photocopying.

FIG. 2 depicts an embodiment of a display of a user interface. A display210 can be used to create, view, confirm, compare, request, edit, orotherwise view or modify information associated with a document 100. Thedisplay 210 can be part of a user interface such as a computing device.The computing device can be a desktop or laptop computer, a tablet, asmart phone and the like. FIG. 2 depicts a display of informationassociated with a document having a mark 206 and an invisible code 208thereon. For example, the display 210 depicts what a user may see when auser types in a serial number from a document, such as the serial number107 described above, into a user interface, or scans a computer readablecode on the document, such as computer readable code 109. The displaywill depict the mark 206 as an indicator that the document has asecurity or traceability feature associated with it. The display 210also displays a version of the invisible code 208, shown in a visibleformat on the display 210, such as a QR code. The display 210 alsoincludes a computer readable code 209 and data fields 220.

The computer readable code 209 can correspond to a computer readablecode located on the document, as described elsewhere herein. In someembodiments, the computer readable code can also encode or be associatedwith a delivery point. The delivery point encoded in the computerreadable code 209 can be the delivery point of a user who ordered,purchased, requested, or received the document.

The data fields 220 include today's date, which can be the day on whichthe user accesses the information about the document, a title of thedocument, a date the document was purchased, and an owner of thedocument. Although these four data fields 220 are shown here, a personof skill in the art, guided by this disclosure, would understand thatthe data fields 220 can include more or fewer or different data fields220 than those depicted here. The types of data fields 200 can also bedifferent for each category of document. FIG. 2 depicts possible datafields 220 for a collectible card, such as a sports card. A vitaldocument or health record can have different information listed in thedata fields, (i.e., date of birth, birth place, Social Security Number,race, etc.), such as the intended recipient, the originating entity, ora list of people authorized to view the document.

A user can access and view the data fields 220 on the display in orderto verify the authenticity of the document. For example, if the usertypes in the serial number 107 or scans the computer readable code 109into a user interface, and the serial number is not recognized, a usercan consider the document a fake or forgery. If the serial number 107 orthe computer readable code 209 does return information from thedatabase, and the information in the data fields does not match what auser expects, this can indicate that a document has been modified, isstolen, is a fake, etc. For example, if a user is contemplating buying asports card, the user can check whether the listed owner corresponds tothe individual selling the sports card. If these do not match, a usercan suspect the document 100 is not authentic, or there is some otherproblem. A user can also use the data fields 220 to show to aprospective buyer or recipient of the document 100 that the document isauthentic, by inputting the serial number 107 into the database, orscanning the computer readable code 109 and showing the prospectivebuyer or recipient the information. A user may also desire to determinethe provenance or title history of a document. The data fields caninclude the title history or ownership history for a document, or thedata fields 220 can include a clickable link (not shown) that can linkto the title history or ownership history for the document, can link tothe transaction history of a document, or can link to any other desiredinformation about the document.

The use, tracking, authentication, and tracing of documents using thefeatures described above will now be described with regard to FIGS. 3-5.FIG. 3 is a flowchart of an exemplary process for creating a cardprotected by a tracking and tracing system described herein.

The process 300 moves to step 304 upon granting the document originatoraccess to the document creation application. The document originatorprovides document information, such as the title of the document 100, arequest to use the tracking and tracing system, the originator of thedocument 100, the origination/creation date of the document 100, theowner of the document, the name of the entity or person requesting thedocument, and the like.

FIG. 3 is a flow chart depicting an embodiment of a process for creatinga secure document. The process for creating a secure document can beperformed by any entity wishing to create a secure document (requestor).The requestor may also originate or generate the physical document, orthe requestor may request that the securing entity originate, orgenerate the physical document. As a non-limiting example, a sports cardmanufacturer or a vital records bureau may wish to create securedocuments as described herein. The requestor can request and receiveinformation from a securing entity, such as the USPS, and generate thephysical document using information received from the securing entity.In some embodiments, the entity wishing to create the secure documentcan send the document information, including images, text, and the like,to the securing entity to generate the physical document. Having thephysical document generated by a securing entity can add an additionallevel of security to the requesting process.

A process 300 begins in step 302, wherein the requestor accesses adocument creation application via a user interface. A securing entitycan operate or access the application in order to provide the securityfeatures and codes for placing on the physical documents. The userinterface can be a mobile application, a web portal, a cloud computingenvironment, a memory resident program running on a computer, and thelike. The requestor can have credentials previously supplied whichverify or confirm the requestor has an account, subscription, etc., withthe document creation application, or are authorized to request documentcreation. A requestor accesses the document creation application using alogin, a token, or other secure method or credential. The documentrequester accesses the document creation application using a securelog-in or other secure credentials. The secure log-in ensures that onlylegitimate document requestors or originators have access to thetracking and tracing system.

The process 300 moves to step 304, wherein the requestor inputs documentinformation, and the document creation application receives documentinformation. In some embodiments, the requestor can provide images orcodes corresponding to the entire document which the application canthen convert or use for printing a physical copy of the document. Forexample, a sports card maker can provide the images, text, and all otherinformation for the sports card to the document creation application,and the document creation application will, itself or using anadditional processor, print or cause to be printed the physical copy ofthe document.

In some embodiments, the requestor provides information about thedocument. In the example of a sports card maker, the sports card makercan provide a description of the card, such as the team name and mascot,a player's name, the type of card (rookie card, achievement, etc.), andthe like. In some embodiments, the requestor can provide a proposed ortarget creation date for the document, or can provide the creation datewhen the document was created. A request to generate the document mayaccompany a document purchase. The document information can include adate and/or an amount of the purchase, and an identity of the purchasingentity. In the example of FIG. 2, the document information can includethe title “Collectible Card”, the date of purchase, “01/01/2017,” andthe owner “Ronald.”

In some embodiments, where the document is being requested by an entityother than the entity that has, makes, or produces the physical versionof the document, the requestor can provide a requestor identity, or acurrent owner information. For example, in the case of a vital record,the vital records bureau may be the requestor using the documentcreation application, the vital record may have been requested byanother entity, such as an individual listed in the vital record(marriage certificate, birth certificate, social security card, etc.) Inthis case, the vital records bureau can include the name, date, etc. ofthe entity requesting the document.

The document information provided to the document creation applicationcan also include an identifier for a delivery point for the document.For example, if a person is requesting a birth certificate from a vitalrecords bureau, or a sports card from a sports card maker, the requestorcan provide the name, address, and date of the person requesting thevital record or the sports card. The composed documented records aregovernment records that include vital information in association withpersonal identification information, encoded and encrypted to protectdata, such as Social Security Numbers, Data of Birth/Birth Certificates,etc.

The process 300 moves to step 306, wherein the document creationapplication generates secure document information. The secure documentinformation can include the mark 106, the serial number 107, theinvisible code 108, the computer readable code 109, or any number orcombination of these. The mark 106, the serial number 107, the invisiblecode 108, and the computer readable code 109 are generated based on theinformation provided by the requestor. The mark 106 can be a standardmark that is applied to all documents using the security systemdescribed herein, or can be tailored or customized for each individualrequestor. For example, a sports card maker can have one unique mark 106that identifies the maker and that the document has authentication andsecurity features; and the vital records bureau can have anotherdifferent, unique mark 106 that identifies the vital records bureau andthe use of the security features described herein. The mark 106 need notspecifically reference the security features, but may indicate tosomeone that security or authentication features are in use with regardto the document on which the mark 106 appears. In some embodiments, arequestor may have one or more lines of documents, such as types ofsports cards, and a unique mark can be provided for each line ofdocuments.

The serial number 107 can be a unique number associated with therequested document, and can be a sequential number, a randomly generatednumber, and the like. The serial number 107 corresponds to the documentbeing requested.

The invisible code 108 is generated based on the EPM™ described herein.In some embodiments, the invisible code 108 is created by first creatinga code associated with or pointing to the record or the documentinformation in the memory or the database. This code is then encryptedusing a secure algorithm to generate a computer readable code. Theencrypted code becomes the invisible code 108 which is ultimately placedon the document. The invisible code 108 can encode the EPM™ or canencode information indicative of the EPM™. The invisible code 108generated for the document can include or be associated with all or anycombination of the document information provided. In order to access thedocument information or the document record, the invisible code 108 mustfirst be read and/or decoded, then, the decoded code must be decryptedto obtain a code that is recognized by and can access the database wherethe document information is stored.

The computer readable code 109 can encode a delivery point, such as a 5to 11 digit ZIP code, or other similar code if mailed outside the UnitedStates, corresponding to on the received delivery destination. In someembodiments, the computer readable code 109 encodes information relatedto the address or the delivery point to which the physical documentbeing requested will be sent.

The document creation application can create a record in a memory ordatabase for each document requested by the requestor. The generatedsecure document information, such as the mark 106, the serial number107, the invisible code 108, and the computer readable code 109 can beassociated with the record for the requested document, and theassociation can be stored in the memory or database with the record, orin a linked or related memory or database. The generated secure documentinformation can be stored with cross-referenced associations such thatthe record for a document, can be identified through any one of theserial number 107, the invisible code 108, or the computer readable code109, or such that any of the generated secure document information canbe identified using any other of the generated secure documentinformation.

The generated secure document information can be provided to therequestor via the user interface. For example, the document creationapplication can provide the mark 106, serial number 107, the invisiblecode 108, or the computer readable code which will printed using aspecialized ink to become the invisible code 108, and the computerreadable code 109. In some embodiments, the generated documentinformation need not be communicated to the requestor, or that only someof the generated secure document information is transmitted to therequestor. For example, in some embodiments, only the serial number 107or only the computer readable code 109 is provided to the requestor.

The process 300 moves to step 308, wherein the physical document isgenerated. The requestor can generate the physical document using atleast a portion of the generated secure document information. In someembodiments, the requestor receives a confirmation that the physicaldocument has been generated by the securing entity, for example, theUSPS, or another entity. The physical document is generated by printingthe document having the generated secure document information thereon,along with the contents of the document provided by the requestor orcreated by the requestor.

The process 300 moves to step 310, wherein the physical document is sentto a recipient. In some embodiments, the recipient can be the requestor.The securing entity can generate the document and send it to therequestor. For example, if a card manufacturer desires to producesecured sports cards in bulk, each having security and tracing features,the card manufacturer can request the securing entity to generate thephysical cards and send those to the requestor, after which therequestor can distribute the cards.

In some embodiments, the requestor provides the secure documentinformation, including the delivery point or intended destination forthe document, as described herein. The securing entity generates thephysical documents including an indicator of the delivery point, such asusing the computer readable code 109. The securing entity can theninduct or place the document in the distribution network, such as themail stream, in the example of the USPS.

In some embodiments, the requestor generates the physical documentitself using the provided secure document information. The requestor caninclude the computer readable code on the physical document. In someembodiments, the invisible code 108 and/or the computer readable code109 can identify an account, or an entity having an account, and thecomputer readable code 109 can encode a postage amount or point to anassociation with an account for paying postage. For example, when therequestor desires to send the physical document to a recipient, therequestor places the physical document in the mail stream, theprocessing equipment scans the invisible code 108 and/or the computerreadable code 109, and can identify a postage account to debit a postagepayment. In some embodiments, the postage payment can be made at anypoint during process 300 and a postage payment can be associated withthe record for the document.

The process 300 moves to step 310, wherein the document is trackedthrough the distribution system and the document record is updated. Asthe physical document moves thorough the distribution network, forexample, the USPS mail stream, various components of processingequipment will scan the physical document, and will read any or all ofthe secure document information printed thereon. At each scan, thelocation, status, identifier for processing equipment on which the itemwas scanned, and any other desired tracking information is obtained andstored. For example, as the physical document moves through the mailstream, the mail processing equipment can scan the computer readablecode 109 and/or the invisible code 108, and update the document recordto reflect the location and status of the physical document, includinginduction, intermediate points, and final delivery of the physicaldocument. In some embodiments, the physical document may be in acontainer, such as an envelope or box, in which the physical document islocated. The container can have the computer readable code 109 thereon,or the container can have a different code thereon which is associatedwith the record for the document.

The process 300 moves to step 314, where the process 300 ends.

FIG. 4 is a flow chart depicting an embodiment of a process foraccessing or viewing secure document information. A process 400 beginsin step 402 wherein a secure document system receives a request fortracking or tracing a document. The request may come from a potentialowner or buyer, or from a document recipient, or any other party, who islooking to see if the document is authentic, to determine itsprovenance, source, chain of title, and the like. In some embodiments,the request can come from an entity who is viewing a document providedby another entity as proof of identity, or to prove the contents of thedocument. For example, where a vital record or bank statement is beingsubmitted to a government entity for issuing a governmentidentification, or to a bank for a loan, to open an account, and thelike, the government entity or the bank may wish to verify theauthenticity of the document. The request can come in the form of aquery via a website or mobile application, for example, where the serialnumber 107 is typed into a field in an application/website associatedwith the securing entity.

The request can come in the form of a scanner input, such as when theinvisible code 108 is read using a scanner capable of reading thespecialized ink with which the invisible code 108 is printed. This canbe done, for example at a USPS facility, using a scanner able to emitthe interrogation signals to illuminate and to read the invisible code108. The scanner sends the scanned codes to a processor which canidentify and/or decode the scanned codes.

After the serial number 107 is entered or the invisible code 108 isscanned, the process 400 moves to decision state 404, wherein it isdetermined whether the serial number 107 and/or the invisible code 108is recognized. Recognizing the invisible code 108 can include decodingthe invisible code 108, decrypting the decoded code, and comparing thedecrypted code to the database for a corresponding or matching entry ordocument record.

If the serial number 107 or the invisible code 108 is not recognized instate 404, the process 400 moves to step 406, wherein the securedocument system returns an error message or displays a message on thewebpage, the mobile computing device, etc., that the serial number 107or invisible code 108 were not recognized, and access is denied.

If the serial number 107 or the invisible code 108 are recognized instate 404, the process 400 moves to step 408, wherein the securedocument information is displayed, for example, as described with regardto FIG. 2. A potential seller or buyer, or recipient who input a serialnumber into the application may see a screen similar to that shown inFIG. 2, which shows today's date, or the date of access, the title ofthe document, the date the document was created, purchased, or any otherrelevant date, the owner or originator of the document, and/or any otherdesired information. In some embodiments, the securing entity can alsodisplay a chain of title or ownership of the document.

Where the request for the secure document information or tracking ortracing comes from a scan of the invisible code 108, some or all theinformation included with the invisible code 108, such as theinformation contained within or wrappered with the EPM™ is available tothe requesting entity. To read the EPM™, the scanner must have not onlythe capability to read the “invisible ink”, but must be connected to acomputer system having the correct encryption/decryption algorithm todecrypt the read code from the invisible code 108. When the invisiblecode 108 is read and decrypted, the document information and securedocument information can be accessed. The information can include whenthe document was created, when it was modified, the scan history of theEPM™, tracking information, and any other desired information can beobtained.

The requesting entity can see the information to determine whether thedocument is owned by the seller of the document, to discover thedocument's provenance, or to determine whether the document wasauthentic. If the serial number is recognized, this can be evidence thatthe document is authentic. If the serial number is not recognized, thisindicates that the document is not authentic. If the informationassociated with the document provided by the securing entity does notmatch what a potential seller, buyer, government officer, bank employee,etc. is not what is expected, this can be evidence that the document isnot authentic.

In some embodiments, the process 400 may end following step 408. Forexample, if a user desires only to check a document's authenticity, theprocess can end after step 408. In some embodiments, a user may desireto update the information associated with the document, such as updatinga purchase date, changing an owner, and the like. The tracking andtracing system can include features and functions to allow documentinformation to be updated. If so, the process 400 moves to step 410,wherein a request to update the document information is received via auser interface.

The process 400 moves to decision state 412, wherein it is determinedwhether the user requesting to update the document information isauthorized to update the document information. A user may have onlyprivileges to view the document information. For example, where a usertypes the serial number into a website, the user will not be allowed tomodify or update the document information. In this case, there may noteven be a login required. If the user is not authorized to update ormodify document information, the process moves to block 406, whereinaccess is denied to modify the document information.

In the case of a scan at a post office, where the securing systemidentifies a postal scanner as reading the invisible code 108, thesecuring system may allow the clerk at the post office to modify thedocument information. In some embodiments, the maker of the sports cardmay be authorized to modify document information. The card maker orvital records bureau may use the same access credentials as were used toprovide the document information to the securing entity to get access tomodify the document information. If the user is authorized to modify thedocument information, the process 400 moves to step 414, wherein themodified document information is received and stored. Then, when a usernext accesses the document information, the modified or updatedinformation will be displayed. In some embodiments, a record of themodification and the user making the modification will be recorded,stored, and will be available to view. In some embodiments, access tomodify the document information may be granted when the invisible code108, such as the EPM™ is successfully read and decrypted. In this case,only a user with access to decrypt the EPM™ are authorized to modify orchange document information.

The process 400 then moves to step 416, wherein the process 400 ends.

FIG. 5 depicts an exemplary process of ordering a secure document via asecuring entity. A process 500 begins in step 502, wherein an entity,such as a user, a business, and the like requests to obtain a securedocument. This request can come in the form of a customer browsing at astore, such as at a collectible card shop. The request can come in theform of an online request or purchase made over the internet. Therequest can be received at an automated kiosk, such as at an automatedpost center.

The process 500 proceeds to decision state 504, wherein it is determinedwhether a secure document such as the type being requested is readilyavailable. In the case where the secure documents are collectible sportscards, secure documents may already have been printed, and may beavailable for purchase at a store.

If it is determined in state 504 that the document, or type of documentbeing requested is readily available, the process 500 moves to step 506,wherein the secure document is provided to the customer. For example,the collectible card can be given to the purchaser in the store. In someembodiments, the secure document can be considered readily available,even if it is not on hand in a store's inventory. For instance, wherethe request for the secure document is made online, the secure documentcan be provided to the recipient by sending it via a distributionnetwork, such as the USPS. In some embodiments, the maker or seller ofsecure documents may have the secure document in an inventory, such as awarehouse, and the maker or seller will ship the secure document to therecipient. In some embodiments, the distribution network may maintain aninventory of secure documents it has generated. When the user requeststhe secure document, the request can be directly to the distributionnetwork, or can be made to the seller of the document, who, in turn,requests the distribution network send the secure document to therecipient. In some embodiments, the computer readable code 109 on thedocument can be associated with a delivery point, such as a streetaddress, for the requestor, and the document can be shipped to thedelivery point without providing any additional information on thedocument. The distribution network's processing equipment can beconfigured to scan and read the computer readable code 109 and sort andprocess the document accordingly. This can be done where the deliverypoint is coded into the computer readable code 109, or where thedelivery point is associated with the computer readable code 109.

If it is determined in state 504 that the document is not readilyavailable, the process moves to step 508, wherein generation of thesecure document is requested. For example, if the document is a vitalrecord, health records, a financial statement, or other similardocument, the secure document may not already exist, and will need to beneed to be created upon request. The process of requesting generation ofthe secure document can be similar to that described with regard to FIG.3.

The process 500 moves to step 510, wherein the document creationinformation is recorded and stored. The document creation informationrecorded and stored can include the name and address of the purchaser orrequestor, the date of purchase or request, creation date, creationtime, creation location, or any other desired information related to thepurchaser or the creation of the secure document. A copy of the documentcreation information can be provided to the requestor or purchaser. Thedocument creation information can be provided to the requestor orpurchaser via the interface used to purchase the secure document, or canbe electronically communicated, such as via email, SMS, and the like.

The process 500 moves to step 512 wherein the secure document isprovided to the recipient or purchaser. As described elsewhere herein,this can include the distribution network shipping the secure documentto the recipient. In some embodiments, the maker, originator, or sellerof the secure document can send or ship the secure document to therecipient, also as described elsewhere herein.

The process 500 moves to step 512 wherein delivery of the securedocument is confirmed. When a delivery resource delivers the physicalversion of the secure document, the delivery resource may scan, using amobile computing device, the computer readable code 109 on the securedocument. This can occur as the document is placed in a mailbox, left ina post office box, an electronic parcel locker, on a doorstep, or in anyother place where the recipient can receive. In some embodiments, thesecure document may require an in-person delivery, or for the deliveryresource to hand the secure document to the recipient, at which pointthe scan can occur. The mobile computing device can communicate the scancoinciding with the delivery event to the secure tracking and tracingsystem. The date, time, type, and location of the delivery event can bestored in the secure document record, or associated with the securedocument in the memory or database. The delivery event can become partof the document information that is accessible through systems andmethods described with regard to FIG. 4.

The process 500 moves to step 516, wherein the securing entity oranother associated entity provides the recipient with accesscredentials, which allow the entity to view the document information viaa computer portal. For example, where the secure document is acollectible sports card, the information can be readily available to anyperson who desires to view the document information, and can be donesimply by entering the serial number 107 into a website. However, if thedocument information is more sensitive, such as a vital or healthrecord, it may be undesirable to allow any entity to access the documentinformation using the serial number 107. In this case, the securingentity can provide access credentials to access the tracking and tracingsystem which will allow a user to access only certain secure documents,for example, to access the secure document delivered to that recipient.

In some embodiments, the access credentials can be provided to therecipient via an email, SMS text message, in a separate physicaldocument sent to the recipient, or as a token loaded onto therecipient's smartphone. In some embodiments, the recipient is notifiedthat the recipient can access the document information by taking thedocument to a specific location having secure networks, such as to thepost office or other location. There, upon providing appropriateidentification, the postal clerk or other entity can scan the invisiblecode 108 and provide the document information to the recipient.

A person of skill in the art, guided by the present disclosure, willunderstand that step 516 can be performed at any time during process500.

The technology is operational with numerous other general purpose orspecial purpose computing system environments or configurations.Examples of well-known computing systems, environments, and/orconfigurations that may be suitable for use with the invention include,but are not limited to, personal computers, server computers, hand-heldor laptop devices, multiprocessor systems, microprocessor-based systems,programmable consumer electronics, network PCs, minicomputers, mainframecomputers, distributed computing environments that include any of theabove systems or devices, and the like.

The present disclosure refers to processor-implemented steps forprocessing information in the system. Instructions can be implemented insoftware, firmware or hardware and include any type of programmed stepundertaken by components of the system.

The one or more processors may be implemented with any combination ofgeneral-purpose microprocessors, microcontrollers, digital signalprocessors (DSPs), field programmable gate arrays (FPGAs), programmablelogic devices (PLDs), controllers, state machines, gated logic, discretehardware components, dedicated hardware finite state machines, or anyother suitable entities that may perform calculations or othermanipulations of information. The system hub 210 may comprise aprocessor 212 such as, for example, a microprocessor, such as a Pentium®processor, a Pentium® Pro processor, a 8051 processor, a MIPS®processor, a Power PC® processor, an Alpha® processor, amicrocontroller, an Intel CORE i7®, i5®, or i3® processor, an AMDPhenom®, A-series®, or FX® processor, or the like. The processorstypically have conventional address lines, conventional data lines, andone or more conventional control lines.

The tracking and tracing system may be used in connection with variousoperating systems such as Linux®, UNIX®, MacOS®, or Microsoft Windows®.

The system control may be written in any conventional programminglanguage such as C, C++, BASIC, Pascal, or Java, and ran under aconventional operating system. C, C++, BASIC, Pascal, Java, and FORTRANare industry standard programming languages for which many commercialcompilers can be used to create executable code. The system control mayalso be written using interpreted languages such as Perl, Python orRuby.

Those of skill will further recognize that the various illustrativelogical blocks, modules, circuits, and algorithm steps described inconnection with the embodiments disclosed herein may be implemented aselectronic hardware, software stored on a computer readable medium andexecutable by a processor, or combinations of both. To clearlyillustrate this interchangeability of hardware and software, variousillustrative components, blocks, modules, circuits, and steps have beendescribed above generally in terms of their functionality. Whether suchfunctionality is implemented as hardware or software depends upon theparticular application and design constraints imposed on the overallsystem. Skilled artisans may implement the described functionality invarying ways for each particular application, but such embodimentdecisions should not be interpreted as causing a departure from thescope of the present invention.

The various illustrative logical blocks, modules, and circuits describedin connection with the embodiments disclosed herein may be implementedor performed with a general purpose processor, a digital signalprocessor (DSP), an application specific integrated circuit (ASIC), afield programmable gate array (FPGA) or other programmable logic device,discrete gate or transistor logic, discrete hardware components, or anycombination thereof designed to perform the functions described herein.A general purpose processor may be a microprocessor, but in thealternative, the processor may be any conventional processor,controller, microcontroller, or state machine. A processor may also beimplemented as a combination of computing devices, e.g., a combinationof a DSP and a microprocessor, a plurality of microprocessors, one ormore microprocessors in conjunction with a DSP core, or any other suchconfiguration.

If implemented in software, the functions may be stored on ortransmitted over as one or more instructions or code on acomputer-readable medium. The steps of a method or algorithm disclosedherein may be implemented in a processor-executable software modulewhich may reside on a computer-readable medium. Memory Computer-readablemedia includes both computer storage media and communication mediaincluding any medium that can be enabled to transfer a computer programfrom one place to another. A storage media may be any available mediathat may be accessed by a computer. By way of example, and notlimitation, such computer-readable media may include RAM, ROM, EEPROM,CD-ROM or other optical disk storage, magnetic disk storage or othermagnetic storage devices, or any other medium that may be used to storedesired program code in the form of instructions or data structures andthat may be accessed by a computer. Also, any connection can be properlytermed a computer-readable medium. Disk and disc, as used herein,includes compact disc (CD), laser disc, optical disc, digital versatiledisc (DVD), floppy disk, and Blu-ray disc where disks usually reproducedata magnetically, while discs reproduce data optically with lasers.Combinations of the above should also be included within the scope ofcomputer-readable media. Additionally, the operations of a method oralgorithm may reside as one or any combination or set of codes andinstructions on a machine readable medium and computer-readable medium,which may be incorporated into a computer program product.

The foregoing description details certain embodiments of the systems,devices, and methods disclosed herein. It will be appreciated, however,that no matter how detailed the foregoing appears in text, the systems,devices, and methods can be practiced in many ways. As is also statedabove, it should be noted that the use of particular terminology whendescribing certain features or aspects of the invention should not betaken to imply that the terminology is being re-defined herein to berestricted to including any specific characteristics of the features oraspects of the technology with which that terminology is associated.

It will be appreciated by those skilled in the art that variousmodifications and changes may be made without departing from the scopeof the described technology. Such modifications and changes are intendedto fall within the scope of the embodiments. It will also be appreciatedby those of skill in the art that parts included in one embodiment areinterchangeable with other embodiments; one or more parts from adepicted embodiment can be included with other depicted embodiments inany combination. For example, any of the various components describedherein and/or depicted in the Figures may be combined, interchanged orexcluded from other embodiments.

With respect to the use of substantially any plural and/or singularterms herein, those having skill in the art can translate from theplural to the singular and/or from the singular to the plural as isappropriate to the context and/or application. The varioussingular/plural permutations may be expressly set forth herein for sakeof clarity.

It will be understood by those within the art that, in general, termsused herein are generally intended as “open” terms (e.g., the term“including” should be interpreted as “including but not limited to,” theterm “having” should be interpreted as “having at least,” the term“includes” should be interpreted as “includes but is not limited to,”etc.). It will be further understood by those within the art that if aspecific number of an introduced claim recitation is intended, such anintent will be explicitly recited in the claim, and in the absence ofsuch recitation no such intent is present. For example, as an aid tounderstanding, the following appended claims may contain usage of theintroductory phrases “at least one” and “one or more” to introduce claimrecitations. However, the use of such phrases should not be construed toimply that the introduction of a claim recitation by the indefinitearticles “a” or “an” limits any particular claim containing suchintroduced claim recitation to embodiments containing only one suchrecitation, even when the same claim includes the introductory phrases“one or more” or “at least one” and indefinite articles such as “a” or“an” (e.g., “a” and/or “an” should typically be interpreted to mean “atleast one” or “one or more”); the same holds true for the use ofdefinite articles used to introduce claim recitations.

In addition, even if a specific number of an introduced claim recitationis explicitly recited, those skilled in the art will recognize that suchrecitation should typically be interpreted to mean at least the recitednumber (e.g., the bare recitation of “two recitations,” without othermodifiers, typically means at least two recitations, or two or morerecitations). Furthermore, in those instances where a conventionanalogous to “at least one of A, B, and C, etc.” is used, in generalsuch a construction is intended in the sense one having skill in the artwould understand the convention (e.g., “a system having at least one ofA, B, and C” would include but not be limited to systems that have Aalone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). In those instances where aconvention analogous to “at least one of A, B, or C, etc.” is used, ingeneral such a construction is intended in the sense one having skill inthe art would understand the convention (e.g., “a system having at leastone of A, B, or C” would include but not be limited to systems that haveA alone, B alone, C alone, A and B together, A and C together, B and Ctogether, and/or A, B, and C together, etc.). It will be furtherunderstood by those within the art that virtually any disjunctive wordand/or phrase presenting two or more alternative terms, whether in thedescription, claims, or drawings, should be understood to contemplatethe possibilities of including one of the terms, either of the terms, orboth terms. For example, the phrase “A or B” will be understood toinclude the possibilities of “A” or “B” or “A and B.”

All references cited herein are incorporated herein by reference intheir entirety. To the extent publications and patents or patentapplications incorporated by reference contradict the disclosurecontained in the specification, the specification is intended tosupersede and/or take precedence over any such contradictory material.

The term “comprising” as used herein is synonymous with “including,”“containing,” or “characterized by,” and is inclusive or open-ended anddoes not exclude additional, unrecited elements or method steps.

The above description discloses several methods and materials of thepresent invention. This invention is susceptible to modifications in themethods and materials, as well as alterations in the fabrication methodsand equipment. Such modifications will become apparent to those skilledin the art from a consideration of this disclosure or practice of theinvention disclosed herein. Consequently, it is not intended that thisinvention be limited to the specific embodiments disclosed herein, butthat it cover all modifications and alternatives coming within the truescope and spirit of the invention as embodied in the attached claims.

What is claimed is:
 1. A system for authenticating a document comprising: a memory storing document information, and a unique identifier and a code associated with the document information; document processing equipment for receiving and processing a physical document, the document processing equipment comprising a scanner configured to scan the unique identifier and the code on a document being processed; a processor in communication with the document processing equipment, the scanner, and the memory, the processor configured to: read the scanned unique identifier; decode the scanned code; query the memory using at least one of the scanned unique identifier and the decoded scanned code to obtain document information; and cause the document information to be displayed.
 2. The system of claim 1, wherein the code is invisible to an unaided human eye.
 3. The system of claim 2, wherein the scanner is configured to interrogate the code with a signal that causes the invisible code to become visible.
 4. The system of claim 2, wherein the document processing equipment is configured to identify an emblem located on the physical document being processed.
 5. The system of claim 4, wherein the code processor is further configured to receive and recognize the emblem, and, in response to recognizing the emblem, cause the scanner to emit an interrogation signal to read the invisible code.
 6. The system of claim 1, wherein the unique identifier is an alphanumeric string.
 7. The system of claim 1 further comprising a user interface configured to receive the unique identifier.
 8. The system of claim 7, wherein the processor is further configured to receive the unique identifier from the user interface and to cause the user interface to display the document information associated with the unique identifier.
 9. The system of claim 8, wherein the scanner is further configured to read a computer readable code on the document being processed, the computer readable code corresponding to the unique identifier.
 10. The system of claim 9, wherein the user interface is further configured to scan the computer readable code on the document and communicate the corresponding unique identifier to the processor.
 11. A method of document validation comprising: storing, in a memory, document information, and a unique identifier and a code associated with the document information; receiving, in document processing equipment, a document having the unique identifier and the code thereon; scanning the document to identify the unique identifier and the code on the document; reading, by a processor, the scanned unique identifier; decoding, by a processor, the scanned code; querying, by a processor, the memory using at least one of the scanned unique identifier and the decoded scanned code to obtain the document information associated with the unique identifier and the code; and displaying the document information.
 12. The method of claim 11, wherein the code is invisible to an unaided human eye.
 13. The method of claim 12, wherein scanning the code comprises interrogating the code with a signal that causes the invisible code to become visible.
 14. The method of claim 12, wherein the received document further comprises an emblem on the document, and wherein scanning the document further comprises scanning the document to identify the emblem.
 15. The method of claim 14, further comprising recognizing, by a processor, the emblem, and, in response to recognizing the emblem, causing the scanner to emit an interrogation signal to read the invisible code.
 16. The method of claim 11, wherein the unique identifier is an alphanumeric string.
 17. The method of claim 1 further comprising receiving, via a user interface, the unique identifier.
 18. The system of claim 17, further comprising receiving, by a processor the unique identifier from the user interface, and causing the user interface to display the document information associated with the unique identifier.
 19. The system of claim 18, wherein the document further comprises a computer readable code on the document being processed, the computer readable code corresponding to the unique identifier.
 20. The system of claim 19, further comprising scanning, by the user interface the computer readable code on the document and obtaining the document information associated with the unique identifier based on the scanned computer readable code. 